Skip to main content

This is a new service – your feedback will help us to improve it.

Boston Borough Council

Brownfield land

There is a problem

  • 15 issue of type invalid category value

BLR/BOS/001

SiteReference
BLR/BOS/001
SiteNameAddress
Whitehorse Lane, Boston
Deliverable
yes
HazardousSubstances
Hectares
0.48
MinNetDwellings
NetDwellingsRangeFrom
50
NetDwellingsRangeTo
60
OwnershipStatus

undefined

2
PermissionDate
2018-06-06
PermissionType
1
PlanningHistory
https://www.boston.gov.uk/planning-application-search/?ref=B/17/0121#https://www.boston.gov.uk/planning-application-search/?ref=B/17/0121
PlanningStatus
1
SiteplanURL
https://www.boston.gov.uk/media/21482/Whitehorse-Lane/pdf/Whitehorse-Lane.pdf?m=638018104293800000
GeoX
POINT(-0.024056 52.974149)
GeoY
POINT(-0.024056 52.974149)
Notes
Planning permission for the development of 60 dwellings (B/17/0121) has been implemented by a small amount of demolition, but is inactive. The site is identified as a housing allocation capable of providing 50 dwellings in the South East Lincolnshire Local Plan 2011-2036: Adopted March 2019, site ref no: Cen001. The site is for sale.. 1. Erection of two apartment blocks, one fronting John Adams Way and the other fronting White Horse Lane, Boston 2. Erection of one dwelling attached to the north gable of 82 High Street, Boston 3. Conversion of Haven Wharf warehouse to provide 21 flats 4. Relevant demolition in a conservation area including the demolition of outbuilding to the rear of 78 High Street Boston, an industrial building attached to the south elevation of Haven Wharf Warehouse and buildings nos 1, 2 and 3
OrganisationLabel
OrganisationURI
LastUpdatedDate
2024-11-19
FirstAddedDate
2017-11-20
EndDate

How to fix this issue

Your dataset is missing the OwnershipStatus column.

The Brownfield land guidance explains how to fix the issue:

OwnershipStatus

Indicate the site’s ownership by entering one of the following values:

How to improve Boston Borough Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL